Method and system for detecting restricted content associated with retrieved content

ABSTRACT

In embodiments of the present invention improved capabilities are described for detecting restricted content associated with retrieved content. The method and system may include receiving a client request for content, saving contextual information from the client request, presenting retrieved content in response to the client request, and presenting the contextual information from the client request, and retrieved content, to a scanning facility. The scanning facility may utilize the contextual information from the client request to aid in the detection of restricted content associated with retrieved content.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.14/838,973 filed Aug. 28, 2015, which is a continuation of U.S. patentapplication Ser. No. 14/168,321 filed Jan. 30, 2014 (now U.S. Pat. No.9,122,874), which is a continuation of U.S. patent application Ser. No.12/055,586 filed Mar. 26, 2008 (now U.S. Pat. No. 8,650,648), each ofwhich is hereby incorporated by reference in its entirety.

BACKGROUND

Field

The present invention is related to secure computing, and morespecifically related to contextual scanning of data for detectingrestricted content.

Description of the Related Art

One aspect of secure computing is the scanning of data as it is receivedfrom a source, such as for the scanning for malware, confidentialmaterials, restricted materials, and the like. Malware may be defined asmalicious software that may infiltrate a computer system with theintention of damaging it. Examples of malware may be computer viruses,computer worms, spyware, adware or any other unwanted software. Currenttechniques for the scanning of data may provide for the blocking ofknown source sites, such as through the use of Uniform ResourceIdentifier (URI) black lists and such, but individuals bent oncircumventing blacklists often change their URIs constantly, evenbreaking the delivery of their content into a series of deliverables,each with their own URI. There exists therefore a need for improvedmethods of scanning data that better utilize information associated withthe client request and the retrieved content.

SUMMARY

In embodiments, identifying content through a scanning facility may bedone for a number of reasons. One reason may be the potential forunintentionally receiving malware, and the need to block the malwareupon reception before the malware has the chance to do any damage.Traditionally, one way malware may be identified is with identity filesutilized by the scanning facility. However, the chances of identifyingthe malware may be greatly increased if the scanning facility is able toscan the received content in light of some information associated withthe file, the address, the URI, the source, the sender, and the like.Similarly, this technique may be used against file transfers that arepotentially less malicious, such unauthorized transfers, downloading oruploading confidential files from within or outside an enterprise, thedownloading or transfer of inappropriate content, and the like. Thepresent invention may allow for a technique, where the content beingretrieved, and information associated with the request or source of theinformation, may both be made available to the scanning facility toincrease the potential for targeted content to be identified.

In embodiments, the present invention may provide for an improved methodand system to detect restricted content associated with retrievedcontent. The method and system may include receiving a client requestfor content, saving contextual information from the client request,presenting retrieved content in response to the client request,presenting the contextual information from the client request andretrieved content to a scanning facility, and the like. The scanningfacility may utilize the contextual information from the client requestto aid in the detection of restricted content associated with theretrieved content.

In embodiments, the contextual information may be extracted from a URIincluded in the client request, where the extracted information may be aplurality of characters from the URI, may exclude the domain name, mayinclude address information irrespective of the domain name, may be adata pattern determined based on a study of how a malicious attacker ischanging the URI, and the like. In embodiments, the contextualinformation may be derived from a URI included in the client request,where data pattern information may be extracted from the URI andcompared to data patterns of target content to derive the contextualinformation. In embodiments, the scanning facility may be a local to theclient, a server based scanning facility, and the like. A client requestrestriction process may be provided in association with a policyfacility such that certain client requests are automatically denied. Inaddition, a remedial action may be performed on the client in responseto the scanning facility blocking of restricted content, where theremedial action may be a scan of a local drive for malicious software.

In embodiments, the client request may be associated with one or more IPaddresses, one or more servers, and the like. The server may be anenterprise server, a root name server or any other server. Theenterprise server may be under the control of an administrator.

In embodiments, the client request may be an address. The address may bea web address, an origin address, a destination address, an emailaddress, a network address, and the like. The address may be associatedwith a device ID, a digital certificate and the like.

In embodiments, the client request may be a URI. The URI may be auniform resource locator (URL). The URI may include a domain name. Thedomain name may be a registered domain name, a top-level domain name andthe like. The domain name may be associated with voice over Internetprotocol (VoIP), domain keys, an email and the like. The top-leveldomain name may be associated with a country.

In embodiments, the URI may include a sub-domain name. The sub-domainname may be associated with a server. In another embodiment, the URI mayinclude a host name.

In embodiments, the URI may be associated with multiple domain names. Inanother embodiment, the URI may be associated with URI redirection.

In embodiments, the client request may be associated with a location.The location may be a geographic location, a business location, aresidence location, a government location, a public location, a privatelocation, a network location, a server location, a district, a region, avicinity, and the like.

In embodiments, the contextual information may be associated with acharacter string within the client request. The character may be analphanumeric character, an alphanumeric code character, an asciicharacter, and the like.

In embodiments, the contextual information may be associated with aportion of a character string within a one or more client requests. Theone or more client requests may be in a sequence. The portion of thecharacter string may be changing from a first client request to a secondclient request. The changing may be a changing numerical sequence, achanging of an alphanumeric sequence, a changing of an alphanumeric codesequence, a changing that increases the value of the portion of thecharacter string, a changing that decreases the value of the portion ofthe character string, a changing that may be associated with a patternof changing.

In embodiments, the contextual information may be associated with aportion of a character string within a one or more client requests. Theportion may be an unchanged portion from a first client request to asecond client request. The unchanged portion may be associated withmalware detection.

In embodiments, the portion of the character string may be compared to alibrary of previously stored portions. The previously stored portionsmay be an unchanging portion, a changing portion.

In embodiments, the portion of the character string may be associatedwith the path taken by the client request. The path may be a relativepath, an absolute path, and the like.

In embodiments, the portion of the character string may be associatedwith the domain of the client request. The portion of the characterstring may change while the domain name stays unchanged. The portion ofthe character string may be associated with the path.

In embodiments, the contextual information may be associated with adownload, a detected pattern in a sequence of URI requests, and thelike.

In embodiments, the contextual information may be associated with pathinformation of the client request. The path information may include oneor more sub-path portions from the origin of the client request to thelocation of the retrieved content.

In embodiments, the contextual information may be associated with pathinformation of the retrieved content. The path information may includeone or more sub-path portions from the location of the retrieved contentto the origin of the client request.

In embodiments, the contextual information may be associated withinformation received along with the retrieved content. The informationmay be header information, path information, location information,domain information, IP address information, network information or anyother information.

In embodiments, the retrieved content may be web content. The webcontent may be a text content, a document, a data file, a visualcontent, an aural content, an application, an e-service, a web page, ablog, a search result, a discussion board, an e-commerce site, a socialnetwork site, a download, a game, an email, an appropriate website, aninappropriate website and the like. The visual content may be an image,a video, an animation, and the like.

In embodiments, the retrieved content may be associated with malware.The malware may be content associated with spam, content associated witha virus, content associated with a worm, content associated with aTrojan horse, content associated with spyware, content associated withadware, and the like.

In embodiments, the retrieved content may be confidential content. Theconfidential content may be company confidential, governmentconfidential or any other confidential content.

In embodiments, the retrieved content may be offensive content. Theoffensive content may be personally offensive, professionally offensive,sexually offensive or offensive in any manner.

In embodiments, the client request restriction may be associated withthe contextual information from the client request. The contextualinformation may include an alphanumeric pattern associated with malware,a domain name pattern associated with malware and the like. Thealphanumeric pattern may be a known alphanumeric string within theclient request, a sequence of alphanumeric strings in a series of clientrequests. The domain name pattern may be associated with a series ofclient requests.

In embodiments, the client request restriction may be associated with acharacteristic of the retrieved content. The characteristic may beassociated with an email message characteristic, an email header, amailing list, a language characteristic. The language characteristic maybe associated with a phrase. The phrase may be a slang. The languagecharacteristic may be associated with one or more words and phrases inproximity to one another.

In embodiments, the client request restriction may be associated with atype of retrieved content. The type may be a webpage, a document, amultimedia file and the like. The multimedia file may be a video file,an audio file, an animation file, an advertisement and the like. Thetype may be an attachment, a download, an email, and the like.

In embodiments, the client request restriction may be associated withthe source of the content. The source of the content may be the sourceof the downloaded content, a local machine and the like. The localmachine may be the machine that created the content, copied the contentor sourced the content in any other manner. In an embodiment, the sourceof the content may be from outside an enterprise. In another embodiment,the source of the content is from inside an enterprise.

In embodiments, the restricted content may be associated withapplication classification. The application classification may bemalware, work product, personal, unapproved, restricted, allowed.

In embodiments, the restricted content may be confidential content. Theconfidential content may be company confidential, governmentconfidential or any other type of confidential content.

In embodiments, the restricted content may be offensive content. Theoffensive content may be personally offensive, professionally offensive,sexually offensive, and the like.

In embodiments, the contextual information may allow the scanningfacility to determine the reputation of the content. The reputation ofthe content may be associated with the source of the content, the authorof the content and the like. The author of the content may be associatedwith an enterprise, a location and the like. The reputation of thecontent may be associated with time. The time may be the time thecontent is created, the time the content is downloaded, the time thecontent is copied, the time the content is requested or any other time.

In embodiments, the present invention may provide an improved method andsystem to detect malware associated with the retrieved content. Themethod and system may include a presenting a client request for content,saving contextual information from the client request, presentingretrieved content associated with the client request, providing a clientrequest restriction in association with a policy facility and presentingthe contextual information from the client request, and retrievedcontent, to a malware detection facility. The malware detection facilitymay utilize the contextual information from the client request to aid inthe detection of malware associated with the retrieved content.

In embodiments, the present invention may provide an improved method andsystem to detect restricted content associated with an electronic file.The method and system may include presenting an electronic file on acomputing facility, extracting locale information from the electronicfile, providing locale restrictions in association with a policyfacility and presenting the locale information and the electronic fileto a scanning facility. The scanning facility may utilize the localeinformation to aid in the detection of restricted content associatedwith the electronic file.

In embodiments, the locale restrictions may be associated with thelocation of the computing facility.

In embodiments, the restricted content may be associated withapplication classification. The application classification may bemalware, work product, personal, unapproved, restricted, allowed, andthe like.

In embodiments, the restricted content may be confidential content. Theconfidential content may be company confidential, governmentconfidential or any other type of confidential content.

In embodiments, the restricted content may be offensive content. Theoffensive content may be personally offensive, professionally offensive,sexually offensive, and the like.

In embodiments, the locale information may allow the scanning facilityto determine the reputation of the content. The reputation of thecontent may be associated with the source of the content, the author ofthe content and the like. The author of the content may be associatedwith an enterprise, a location and the like. The reputation of thecontent may be associated with time. The time may be the time thecontent is created, the time the content is downloaded, the time thecontent is copied, the time the content is requested or any other time.

In embodiments, the locale information may be associated with alocation. The location may be a geographic location, a businesslocation, a residence location, a government location, a publiclocation, a private location, a network location, a server location, adistrict, a region, a vicinity, and the like.

In embodiments, the locale information may be associated with a domainname, a path, a file name, file header information, a current location,a previous location, a user location or any other location within oroutside an enterprise network.

In embodiments, the electronic file may be retrieved from a file system,a network or any other computer system. The file may be retrieved bydownloading.

In embodiments, the electronic file may be a word processing document, aspread sheet document, an image file, an audio file, an email, anapplication file, a web page, a web content page, a database file, asource code file, an operating system file, and the like.

In embodiments, the present invention may provide an improved method andsystem to detect malware associated with an electronic file. The methodand system may include presenting an electronic file on a computingfacility, extracting locale information from the electronic file,providing locale restrictions in association with a policy facility andpresenting the locale information and the electronic file to a malwaredetection facility. The malware detection facility may utilize thelocale information to aid in the detection of malware associated withthe electronic file.

These and other systems, methods, objects, features, and advantages ofthe present invention will be apparent to those skilled in the art fromthe following detailed description of the preferred embodiment and thedrawings. All documents mentioned herein are hereby incorporated intheir entirety by reference.

BRIEF DESCRIPTION OF THE FIGURES

The invention and the following detailed description of certainembodiments thereof may be understood by reference to the followingfigures:

FIG. 1 depicts a block diagram of a threat management facility providingprotection to an enterprise against a plurality of threats.

FIG. 2 depicts a flow diagram embodiment for contextual scanning inassociation with a client request.

FIG. 3 depicts a flow diagram embodiment for contextual scanning inassociation with the locale of a requested file.

FIG. 4 depicts a flow diagram embodiment for detecting restrictedcontent by analyzing contextual information and retrieved contentassociated with the requested content.

FIG. 5 depicts a flow diagram embodiment for detecting malware byanalyzing contextual information and retrieved content associated withthe requested content.

FIG. 6 depicts a flow diagram embodiment for detecting restrictedcontent associated with an electronic file.

FIG. 7 depicts a flow diagram embodiment for detecting malwareassociated with an electronic file.

While the invention has been described in connection with certainpreferred embodiments, other embodiments would be understood by one ofordinary skill in the art and are encompassed herein

All documents referenced herein are hereby incorporated by reference

DETAILED DESCRIPTION

FIG. 1 depicts a block diagram of a threat management facility providingprotection to an enterprise against a plurality of threats. An aspect ofthe present invention relates to corporate policy management and theirimplementation through a unified threat management facility 100. As willbe explained in more detail below, a threat management facility 100 isused to protect computer assets from many threats, both computergenerated threats and user generated threats. The threat managementfacility 100 is multi-dimensional in that it is designed to protectcorporate assets from a variety of threats and it is adapted to learnabout threats in one dimension (e.g. worm detection) and apply theknowledge in another dimension (e.g. spam detection). Corporate policymanagement is one of the dimensions for which the threat managementfacility can control. The corporation may institute a policy thatprevents certain people (e.g. employees, groups of employees, types ofemployees, guest of the corporation, etc.) from accessing certain typesof computer programs. For example, the corporation may elect to preventits accounting department from using a particular version of an instantmessaging service or all such services. In this example, the policymanagement facility 112 may be used to update the policies of allcorporate computing assets with a proper policy control facility or itmay update a select few. By using the threat management facility 100 tofacilitate the setting, updating and control of such policies thecorporation only needs to be concerned with keeping the threatmanagement facility 100 up to date on such policies. The threatmanagement facility 100 can take care of updating all of the othercorporate computing assets.

It should be understood that the threat management facility 100 mayprovide multiple services and policy management may be offered as one ofthe services. We will now turn to a description of the threat managementsystem 100

Over recent years, malware has become a major problem across theinternet 154. From both technical and user perspectives thecategorization of a specific threat type, such as whether it is a virus,worm, spam, phishing exploration, spyware, adware, or the like, isbecoming reduced in significance. The threat, no matter how it'scategorized, may need to be stopped at all points of the enterprisefacility 102, including laptop, desktop, server facility 142, gateway,and the like. Similarly, there may be less and less benefit to the userin having different solutions for known and unknown threats. As such, aconsolidated threat management facility 100 may need to be applied tothe same set of technologies and capabilities for all threats. Thethreat management facility 100 may provide a single agent on thedesktop, and a single scan of any suspect file. This approach mayeliminate the inevitable overlaps and gaps in protection caused bytreating viruses and spyware as separate problems, while simultaneouslysimplifying administration and minimizing desktop load. As the numberand range of types of threats has increased, so may have the level ofconnectivity available to all IT users. This may have lead to a rapidincrease in the speed at which threats may move. Today, an unprotectedPC connected to the internet 154 may be infected quickly, say within 10minutes, which may require acceleration for the delivery of threatprotection. Where once, monthly updates may have been sufficient, thethreat management facility 100 may automatically and seamlessly updateits product set against spam and virus threats quickly, for instance,every five minutes, every minute, continuously, or the like. Analysisand testing may be increasingly automated, and also may be performedmore frequently; for instance, it may be completed in 15 minutes, andmay do so without compromising quality. The threat management facility100 may also extend techniques that may have been developed for virusand malware protection, and provide them to enterprise facility 102network administrators to better control their environments. In additionto stopping malicious code, the threat management facility 100 mayprovide policy management that may be able to control legitimateapplications, such as VoIP, instant messaging, peer-to-peerfile-sharing, and the like, that may undermine productivity and networkperformance within the enterprise facility 102.

The threat management facility 100 may provide an enterprise facility102 protection from computer-based malware, including viruses, spyware,adware, Trojans, intrusion, spam, policy abuse, uncontrolled access, andthe like, where the enterprise facility 102 may be any entity with anetworked computer-based infrastructure. In an embodiment, FIG. 1 maydepict a block diagram of the threat management facility providingprotection to an enterprise against a plurality of threats. Theenterprise facility 102 may be corporate, commercial, educational,governmental, or the like, and the enterprise facility's 102 computernetwork may be distributed amongst a plurality of facilities, and in aplurality of geographical locations. The threat management facility 100may include a plurality of functions, such as security managementfacility 122, policy management facility 112, update facility 120,definitions facility 114, network access rules facility 124, remedialaction facility 128, detection techniques facility 130, testing facility118, threat research facility 132, and the like. In embodiments, thethreat protection provided by the threat management facility 100 mayextend beyond the network boundaries of the enterprise facility 102 toinclude enterprise facility 102 client facility's 144 that have movedinto network connectivity not directly associated or controlled by theenterprise facility 102. Threats to enterprise facility 102 clientfacilities 144 may come from a plurality of sources, such as fromnetwork threats 104, physical proximity threats 110, secondary locationthreats 108, and the like. In embodiments, the threat managementfacility 100 may provide an enterprise facility 102 protection from aplurality of threats to multiplatform computer resources in a pluralityof locations and network configurations, with an integrated systemapproach.

In embodiments, the threat management facility 100 may be provided as astand-alone solution. In other embodiments, the threat managementfacility 100 may be integrated into a third-party product. Anapplication programming interface (e.g. a source code interface) may beprovided such that the threat management facility 100 may be integrated.For instance, the threat management facility 100 may be stand-alone inthat it provides direct threat protection to an enterprise or computerresource, where protection is subscribed to directly with the threatmanagement facility 100. Alternatively, the threat management facilitymay offer protection indirectly, through a third-party product, where anenterprise may subscribe to services through the third-party product,and threat protection to the enterprise may be provided by the threatmanagement facility 100 through the third-party product.

The security management facility 122 may include a plurality of elementsthat provide protection from malware to enterprise facility 102 computerresources, including endpoint security and control, email security andcontrol, web security and control, control of unauthorized users,control of guest and non-compliant computers, and the like. The securitymanagement facility 122 may be a software application that may providemalicious code and malicious application protection to a client facility144 computing resource. The security management facility 122 may havethe ability to scan the client facility 144 files for malicious code,remove or quarantine certain applications and files, prevent certainactions, perform remedial actions and perform other security measures.In embodiments, scanning the client facility 144 may include scanningsome or all of the files stored to the client facility 144 on a periodicbasis, may scan applications once the application has been requested toexecute, may scan files as the files are transmitted to or from theclient facility 144, or the like. The scanning of the applications andfiles may be to detect known malicious code or known unwantedapplications. In an embodiment, new malicious code and unwantedapplications may be continually developed and distributed, and updatesto the known code database may be provided on a periodic basis, on ademand basis, on an alert basis, or the like.

In an embodiment, the security management facility 122 may provide foremail security and control, where security management may help toeliminate spam, viruses, spyware and phishing, control of email content,and the like. The security management facilities 122 email security andcontrol may protect against inbound and outbound threats, protect emailinfrastructure, prevent data leakage, provide spam filtering, and thelike. In an embodiment, security management facility 122 may provide forweb security and control, where security management may help to detector block viruses, spyware, malware, unwanted applications, help controlweb browsing, and the like, which may provide comprehensive web accesscontrol enabling safe, productive web browsing. Web security and controlmay provide internet use policies, reporting on suspect devices,security and content filtering, active monitoring of network traffic,URI filtering, and the like. In an embodiment, the security managementfacility 122 may provide for network access control, which may providecontrol over network connections. Network control may stop unauthorized,guest, or non-compliant systems from accessing networks, and may controlnetwork traffic that may not be bypassed from the client level. Inaddition, network access control may control access to virtual privatenetworks (VPN), where VPNs may be a communications network tunneledthrough another network, establishing a logical connection acting as avirtual network. In embodiments, a VPN may be treated in the same manneras a physical network.

In an embodiment, the security management facility 122 may provide forhost intrusion prevention through behavioral based protection, which mayguard against unknown threats by analyzing behavior before software codeexecutes. Behavioral based protection may monitor code when it runs andintervene if the code is deemed to be suspicious or malicious.Advantages of behavioral based protection over runtime protection mayinclude code being prevented from running, whereas runtime protectionmay only interrupt code that has already partly executed; behavioralprotection may identify malicious code at the gateway or on the fileservers and deletes it before reaching end-point computers and the like.

In an embodiment, the security management facility 122 may provide forreputation filtering, which may target or identify sources of knownmalware. For instance, reputation filtering may include lists of URIs ofknown sources of malware or known suspicious IP addresses, or domains,say for spam, that when detected may invoke an action by the threatmanagement facility 100, such as dropping them immediately. By droppingthe source before any interaction can initiate, potential threat sourcesmay be thwarted before any exchange of data can be made.

In embodiments, information may be sent from the enterprise back to athird party, a vendor, or the like, which may lead to improvedperformance of the threat management facility 100. For example, thetypes, times, and number of virus interactions that a client experiencesmay provide useful information for the preventions of future virusthreats. This type of feedback may be useful for any aspect of threatdetection. Feedback of information may also be associated with behaviorsof individuals within the enterprise, such as being associated with mostcommon violations of policy, network access, unauthorized applicationloading, unauthorized external device use, and the like. In embodiments,this type of information feedback may enable the evaluation or profilingof client actions that are violations of policy that may provide apredictive model for the improvement of enterprise policies.

In an embodiment, the security management facility 122 may provide forthe overall security of the enterprise facility 102 network or set ofenterprise facility 102 networks, may provide updates of malicious codeinformation to the enterprise facility 102 network, and associatedclient facilities 144. The updates may be a planned update, an update inreaction to a threat notice, an update in reaction to a request for anupdate, an update based on a search of known malicious code information,or the like. The administration facility 134 may provide control overthe security management facility 122 when updates are performed. Theupdates may be automatically transmitted without an administrationfacility's 134 direct control, manually transmitted by theadministration facility 134, or the like. The security managementfacility 122 may include the management of receiving malicious codedescriptions from a provider, distribution of malicious codedescriptions to enterprise facility 102 networks, distribution ofmalicious code descriptions to client facilities 144, or the like. In anembodiment, the management of malicious code information may be providedto the enterprise facility's 102 network, where the enterprisefacility's 102 network may provide the malicious code informationthrough the enterprise facility's 102 network distribution system.

The threat management facility 100 may provide policy managementfacility 112 that may be able to block non-malicious applications, suchas VoIP 164, instant messaging 162, peer-to-peer file-sharing, and thelike, that may undermine productivity and network performance within theenterprise facility 102. The policy management facility 112 may be a setof rules or policies that may indicate enterprise facility 102 accesspermissions for the client facility 144, such as access permissionsassociated with the network, applications, external computer devices,and the like. The policy management facility 112 may include a database,a text file, a combination of databases and text files, or the like. Inan embodiment, a policy database may be a block list, a black list, anallowed list, a white list, or the like that may provide a list ofenterprise facility 102 external network locations/applications that mayor may not be accessed by the client facility 144. The policy managementfacility 112 may include rules that may be interpreted with respect toan enterprise facility 102 network access request to determine if therequest should be allowed. The rules may provide a generic rule for thetype of access that may be granted; the rules may be related to thepolicies of an enterprise facility 102 for access rights for theenterprise facility's 102 client facility 144. For example, there may bea rule that does not permit access to sporting websites. When a websiteis requested by the client facility 144, a security facility may accessthe rules within a policy facility to determine if the requested accessis related to a sporting website. In an embodiment, the securityfacility may analyze the requested website to determine if the websitematches with any of the policy facility rules.

The policy management facility 112 may be similar to the securitymanagement facility 122 but with the distribution of enterprise facility102 wide access rules and policies that may maintain control of theaccess of client facility 144 to enterprise facility 102 networkresources. The policies may be defined for application type, subset ofapplication capabilities, organization hierarchy, computer facilitytype, user type, network location, time of day, connection type, or thelike. Policies may be maintained by the administration facility 134,through the threat management facility 100, in association with a thirdparty, or the like. For example, a policy may restrict IM 162 activityto only support personnel for communicating with customers. This mayallow communication for departments requiring access, but may maintainthe network bandwidth for other activities by restricting the use of IM162 to only the personnel that need access to IM 162 in support of theenterprise facility 102. In an embodiment, the policy managementfacility 112 may be a standalone application, may be part of the policymanagement facility 112, network server facility 142, may be part of theenterprise facility 102 network, may be part of the client facility 144,or the like.

In embodiments, the threat management facility 100 may provideconfiguration management, which may be similar to policy management, butmay specifically examine the configuration set of applications,operating systems, hardware, and the like, and managing changes to theirconfigurations. Assessment of a configuration may be made against astandard configuration policy, detection of configuration changes,remediation of improper configuration, application of newconfigurations, and the like. An enterprise may keep a set of standardconfiguration rules and policies which may represent the desired stateof the device. For example, a client firewall may be running andinstalled, but in the disabled state, where remediation may be to enablethe firewall. In another example, the enterprise may set a rule thatdisallows the use of USB disks, and sends a configuration change to allclients, which turns off USB drive access via a registry.

In embodiments, the threat management facility 100 may also provide forthe removal of applications that may interfere with the operation of thethreat management facility 100, such as competitor products that mayalso be attempting similar threat management functions. The removal ofsuch products may be initiated automatically whenever such products aredetected. In the case where such applications are services are providedindirectly through a third-party product, the application may besuspended until action is taken to remove or disable the third-partyproduct's protection facility.

Threat management against a sometimes quickly evolving malwareenvironment may require timely updates, and the update managementfacility 120 may be provided by the threat management facility 100. Inaddition, a policy management facility 112 may also require updatemanagement (e.g. as provided by the update facility 120 hereindescribed), as the enterprise facility 102 requirements for policieschange enterprise facility 102, client facility 144, server facility 142enterprise facility 102. The update management for the security facility122 and policy management facility 112 may be provided directly by thethreat management facility 100, such as by a hosted system or inconjunction with the administration facility 134. In embodiments, thethreat management facility 100 may provide for patch management, where apatch may be an update to an operating system, an application, a systemtool, or the like, where one of the reasons for the patch is to reducevulnerability to threats.

In embodiments, the security facility 122 and policy management facility112 may push information to the enterprise facility 102 network and/orclient facility 144, the enterprise facility 102 network and/or clientfacility 144 may pull information from the security facility 122 andpolicy management facility 112 network server facilities 142, there maybe a combination of pushing and pulling of information between thesecurity facility 122 and the policy management facility 112 networkservers 142, enterprise facility 102 network, and client facilities 144,or the like. For example, the enterprise facility 102 network and/orclient facility 144 may pull information from the security facility 122and policy management facility 112 network server facility 142 mayrequest the information using the security facility 122 and policymanagement facility 112 update module; the request may be based on acertain time period, by a certain time, by a date, on demand, or thelike. In another example, the security facility 122 and policymanagement facility 112 network servers 142 may push the information tothe enterprise facility's 102 network and/or client facility 144 byproviding notification that there are updates available for download andthen transmitting the information. The combination of the securitymanagement 122 network server facility 142 and security update modulemay function substantially the same as the policy management facility112 network server and policy update module by providing information tothe enterprise facility 102 network and the client facility 144 in apush or pull method. In an embodiment, the policy management facility112 and the security facility 122 management update modules may work inconcert to provide all the needed information to the enterprisefacility's 102 network and/or client facility 144 for control ofapplication execution. In an embodiment, the policy update module andsecurity update module may be combined into a single update module.

As threats are identified and characterized, the threat managementfacility 100 may create definition updates that may be used to allow thethreat management facility 100 to detect and remediate the latestmalicious software, unwanted applications, configuration and policychanges, and the like. The threat definition facility 114 may containthreat identification updates, also referred to as definition files. Adefinition file may be a virus identity file that may includedefinitions of known or potential malicious code. The IDE definitionfiles may provide information that may identify malicious code withinfiles, applications, or the like. The definition files may be accessedby security management facility 122 when scanning files or applicationswithin the client facility 144 for the determination of malicious codethat may be within the file or application. The definition files maycontain a number of commands, definitions, or instructions, to be parsedand acted upon, or the like. In embodiments, the client facility 144 maybe updated with new definition files periodically to provide the clientfacility 144 with the most recent malicious code definitions; theupdating may be performed on a set time period, may be updated on demandfrom the client facility 144, may be updated on demand from the network,may be updated on a received malicious code alert, or the like. In anembodiment, the client facility 144 may request an update to thedefinition files from an update facility 120 within the network, mayrequest updated definition files from a computing facility external tothe network, updated definition files may be provided to the clientfacility 114 from within the network, definition files may be providedto the client facility 144 from an external computing facility from anexternal network, or the like.

In an embodiment, a definition management facility 114 may provide forthe timely updates of definition files information to the network,client facilities 144, and the like. New and altered malicious code andmalicious applications may be continually created and distributed tonetworks worldwide. The definition files that maintain the definitionsof the malicious code and malicious application information for theprotection of the networks and client facilities 144 may need continualupdating to provide continual defense of the network and client facility144 from the malicious code and malicious applications. The definitionfiles management may provide for automatic and manual methods ofupdating the definition files. In embodiments, the network may receivedefinition files and distribute the definition files to the networkclient facilities 144, the client facilities 144 may receive thedefinition files directly, or the network and client facilities 144 mayboth receive the definition files, or the like. In an embodiment, thedefinition files may be updated on a fixed periodic basis, on demand bythe network and/or the client facility 144, as a result of an alert of anew malicious code or malicious application, or the like. In anembodiment, the definition files may be released as a supplemental fileto an existing definition files to provide for rapid updating of thedefinition files.

In a similar manner, the security management facility 122 may be used toscan an outgoing file and verify that the outgoing file is permitted tobe transmitted per the enterprise facility 102 rules and policies. Bychecking outgoing files, the security management facility 122 may beable discover malicious code infected files that were not detected asincoming files as a result of the client facility 144 having beenupdated with either new definition files or policy management facility112 information. The definition files may discover the malicious codeinfected file by having received updates of developing malicious codefrom the administration facility 134, updates from a definition filesprovider, or the like. The policy management facility 112 may discoverthe malicious code infected file by having received new updates from theadministration facility 134, from a rules provider, or the like.

The threat management facility 100 may provide for a way to controlaccess to the enterprise facility 102 networks. For instance, theenterprise facility 102 may want to restrict access to certainapplications, networks, files, printers, servers, databases, or thelike. In addition, the enterprise facility 102 may want to restrict useraccess under certain conditions, such as the user's location, usagehistory, need to know, job position, connection type, time of day,method of authentication, client-system configuration, or the like.Network access rules may be developed by the enterprise facility 102, orpre-packaged by a supplier, and managed by the threat managementfacility 100 in conjunction with the administration facility 134.Network access rules and control may be responsible for determining if aclient facility 144 application should be granted access to a requestednetwork location. The network location may be on the same network as thefacility or may be on another network. In an embodiment, the networkaccess control may verify access rights for client facilities 144 fromwithin the network or may verify access rights of computer facilitiesfrom external networks. When network access for a client facility 144 isdenied, the network access control may send an information file to theclient facility 144, the information file may contain data or commandsthat may provide instructions for the remedial action facility 128. Theinformation sent by the network access facility 124 control may be adata file. The data file may contain a number of commands, definitions,instructions, or commands to be parsed and acted upon through theremedial action facility 128, or the like. The information sent by thenetwork access facility 124 control may be a command or command filethat the remedial action facility 128 may access and take action upon.

In an embodiment, the network access rules 124 may provide aninformation store to be accessed by the network access control. Thenetwork access rules facility 124 may include databases such as a blocklist, a black list, an allowed list, a white list, an unacceptablenetwork site database, an acceptable network site database, a networksite reputation database, or the like of network access locations thatmay or may not be accessed by the client facility 144. Additionally, thenetwork access rules facility 124 may incorporate rule evaluation; therule evaluation may parse network access requests and apply the parsedinformation to network access rules. The network access rule facility124 may have a generic set of rules that may be in support of anenterprise facility's 102 network access policies, such as denyingaccess to certain types of websites 158, controlling instant messenger162 accesses, or the like. Rule evaluation may include regularexpression rule evaluation, or other rule evaluation method forinterpreting the network access request and comparing the interpretationto the established rules for network access. In an embodiment, thenetwork access rules facility 124 may receive a rules evaluation requestfrom the network access control and may return the rules evaluation tothe network access control.

Similar to the threat definitions facility 114, the network access rulefacility 124 may provide updated rules and policies to the networkaccess rules facility 124. The network access rules facility 124 may bemaintained by the network administration facility 134 using the networkaccess rules facility 124 management. In an embodiment, the networkadministration facility 134 may be able to maintain a set of accessrules manually by adding rules, changing rules, deleting rules, or thelike. Additionally, the administration facility 134 may be able toretrieve predefined rule sets from a provider that may provide a set ofrules to be applied to an entire enterprise facility 102. The networkadministration facility 134 may be able to modify the predefined rulesas needed for a particular enterprise facility 102 using the networkaccess rules management facility 124.

When a threat or policy violation is detected by the threat managementfacility 100, the threat management facility 100 may provide for aremedial action facility 128. Remedial action may take a plurality offorms, such as terminating or modifying an ongoing process orinteraction, sending a warning to a client or administration facility134 of an ongoing process or interaction, executing a program orapplication to remediate against a threat or violation, recordinteractions for subsequent evaluation, or the like. Remedial action maybe associated with an application that responds to information that aclient facility 144 network access request has been denied. In anembodiment, when the data file is received, remedial action may parsethe data file, interpret the various aspects of the data file, and acton the parsed data file information to determine actions to be taken onan application requesting access to a denied network location. In anembodiment, when the data file is received, remedial action may accessthe threat definitions to parse the data file and determine an action tobe taken on an application requesting access to a denied networklocation. In an embodiment, the information received from the facilitymay be a command or a command file. The remedial action facility maycarry out any commands that are received or parsed from a data file fromthe facility without performing any interpretation of the commands. Inan embodiment, the remedial action facility may interact with thereceived information and may perform various actions on a clientrequesting access to a denied network location. The action may be one ormore of continuing to block all requests to a denied network location, amalicious code scan on the application, a malicious code scan on theclient facility 144, quarantine of the application, terminating theapplication, isolation of the application, isolation of the clientfacility 144 to a location within the network that restricts networkaccess, blocking a network access port from a client facility 144,reporting the application to a administration facility 134, or the like.

Remedial action may be provided as a result of a detection of a threator violation. The detection techniques facility 130 may includemonitoring the enterprise facility 102 network or end-point devices,such as by monitoring streaming data through the gateway, across thenetwork, through routers and hubs, and the like. The detectiontechniques facility 130 may include monitoring activity and stored fileson computing facilities, such as on server facilities 142, desktopcomputers, laptop computers, other mobile computing devices, and thelike. Detection techniques, such as scanning a computer's stored files,may provide the capability of checking files for stored threats, eitherin the active or passive state. Detection techniques, such as streamingfile management, may provide the capability of checking files receivedat the network, gateway facility, client facility 144, and the like.This may provide the capability of not allowing a streaming file orportions of the streaming file containing malicious code from enteringthe client facility 144, gateway facility, or network. In an embodiment,the streaming file may be broken into blocks of information, and aplurality of virus identities may be used to check each of the blocks ofinformation for malicious code. In an embodiment, any blocks that arenot determined to be clear of malicious code may not be delivered to theclient facility 144, gateway facility, or network.

Verifying that the threat management facility 100 is detecting threatsand violations to established policy, may require the ability to testthe system, either at the system level or for a particular computingcomponent. The testing facility 118 may allow the administrationfacility 134 to coordinate the testing of the security configurations ofclient facility 144 computing facilities on a network. Theadministration facility 134 may be able to send test files to a set ofclient facility 144 computing facilities to test the ability of theclient facility 144 to determine acceptability of the test file. Afterthe test file has been transmitted, a recording facility may record theactions taken by the client facility 144 in reaction to the test file.The recording facility may aggregate the testing information from theclient facility 144 and report the testing information to theadministration facility 134. The administration facility 134 may be ableto determine the level of preparedness of the client facility 144computing facilities by the reported information. Remedial action may betaken for any of the client facility 144 computing facilities asdetermined by the administration facility 134; remedial action may betaken by the administration facility 134 or by the user of the clientfacility 144.

The threat research facility 132 may provide a continuously ongoingeffort to maintain the threat protection capabilities of the threatmanagement facility 100 in light of continuous generation of new orevolved forms of malware. Threat research may include researchers andanalysts working on known and emerging malware, such as viruses,rootkits a spyware, as well as other computer threats such as phishing,spam, scams, and the like. In embodiments, through threat research, thethreat management facility 100 may be able to provide swift, globalresponses to the latest threats.

The threat management facility 100 may provide threat protection to theenterprise facility 102, where the enterprise facility 102 may include aplurality of networked components, such as client facility 144, serverfacility 142, DNS server facility 210, administration facility 134,firewall 138, gateway, hubs 148, routers, threat management appliance140, desktop users, mobile users, and the like. In embodiments, it maybe the end-point computer security facility 152, located on a computer'sdesktop, which may provide threat protection to a user, and associatedenterprise facility 102. In embodiments, the term end-point may refer toa computer system that may source data, receive data, evaluate data,buffer data, or the like, such as a user's desktop computer as anend-point computer, a firewall as a data evaluation end-point computersystem, a laptop as a mobile end-point computer, a PDA as a hand-heldend-point computer. In embodiments, end-point may refer to a source ordestination for data, including such components where the destination ischaracterized by an evaluation point for data, and where the data may besent to a subsequent destination after evaluation. The end-pointcomputer security facility 152 may be an application loaded onto thecomputer platform or computer support component, where the applicationmay accommodate the plurality of computer platforms and/or functionalrequirements of the component. For instance, a client facility 144computer may be one of a plurality of computer platforms, such asWindows, Macintosh, Linux, and the like, where the end-point computersecurity facility 152 may be adapted to the specific platform, whilemaintaining a uniform product and product services across platforms.Additionally, components may have different functions to serve withinthe enterprise facility's 102 networked computer-based infrastructure.For instance, computer support components provided as hubs 148, routers,server facility 142, DNS server facility 210, firewalls 138, and thelike, may require unique security application software to protect theirportion of the system infrastructure, while providing an element in anintegrated threat management system that extends out beyond the threatmanagement facility 100 to incorporate all computer resources under itsprotection.

The enterprise facility 102 may include a plurality of client facility144 computing platforms on which the end-point computer securityfacility 152 is adapted. A client facility 144 computing platform may bea computer system that is able to access a service on another computer,such as a server facility 142, via a network. This client facility 144server facility 142 model may apply to a plurality of networkedapplications, such as a client facility 144 connecting to an enterprisefacility 102 application server facility 142, a web browser clientfacility 144 connecting to a web server facility 142, an e-mail clientfacility 144 retrieving e-mail from an internet 154 service provider'smail storage servers 142, and the like. In embodiments, traditionallarge client facility 144 applications may be switched to websites,which may increase the browser's role as a client facility 144. Clients144 may be classified as a function of the extent to which they performtheir own processing. For instance, client facilities 144 are sometimesclassified as a fat client facility 144 or thin client facility 144. Thefat client facility 144, also known as a thick client facility 144 orrich client facility 144, may be a client facility 144 that performs thebulk of data processing operations itself, and does not necessarily relyon the server facility 142. The fat client facility 144 may be mostcommon in the form of a personal computer, where the personal computermay operate independent of any server facility 142. Programmingenvironments for fat clients 144 may include CURI, Delphi, Droplets,Java, win32, X11, and the like. Thin clients 144 may offer minimalprocessing capabilities, for instance, the thin client facility 144 mayprimarily provide a graphical user interface provided by an applicationserver facility 142, which may perform the bulk of any required dataprocessing. Programming environments for thin clients 144 may includeJavaScript/AJAX, ASP, JSP, Ruby on Rails, Python's Django, PHP, and thelike. The client facility 144 may also be a mix of the two, such asprocessing data locally, but relying on a server facility 142 for datastorage. As a result, this hybrid client facility 144 may providebenefits from both the fat client facility 144 type, such as multimediasupport and high performance, and the thin client facility 144 type,such as high manageability and flexibility. In embodiments, the threatmanagement facility 100, and associated end-point computer securityfacility 152, may provide seamless threat protection to the plurality ofclients 144, and client facility 144 types, across the enterprisefacility 102.

The enterprise facility 102 may include a plurality of server facility142, such as application servers 142, communications servers 142, fileservers 142, database servers 142, proxy servers 142, mail servers 142,fax servers 142, game servers 142, web servers 142, and the like. Aserver facility 142, which may also be referred to as a server facility142 application, server facility 142 operating system, server facility142 computer, or the like, may be an application program or operatingsystem that accepts client facility 144 connections in order to servicerequests from clients 144. The server facility 142 application may runon the same computer as the client facility 144 using it, or the serverfacility 142 and the client facility 144 may be running on differentcomputers and communicating across the network. Server facility 142applications may be divided among server facility 142 computers, withthe dividing depending upon the workload. For instance, under light loadconditions all server facility 142 applications may run on a singlecomputer and under heavy load conditions a single server facility 142application may run on multiple computers. In embodiments, the threatmanagement facility 100 may provide threat protection to serverfacilities 142 within the enterprise facility 102 as load conditions andapplication changes are made.

A server facility 142 may also be an appliance facility 140, where theappliance facility 140 provides specific services onto the network.Though the appliance facility 140 is a server facility 142 computer,that may be loaded with a server facility 142 operating system andserver facility 142 application, the enterprise facility 102 user maynot need to configure it, as the configuration may have been performedby a third party. In an embodiment, an enterprise facility 102 appliancemay be a server facility 142 appliance that has been configured andadapted for use with the threat management facility 100, and locatedwithin the facilities of the enterprise facility 102. The enterprisefacility's 102 threat management appliance may enable the enterprisefacility 102 to administer an on-site local managed threat protectionconfiguration, where the administration facility 134 may access thethreat resources through an interface, such as a web portal. In analternate embodiment, the enterprise facility 102 may be managedremotely from a third party, vendor, or the like, without an appliancefacility 140 located within the enterprise facility 102. In thisinstance, the appliance functionality may be a shared hardware productbetween pluralities of enterprises 102. In embodiments, the appliancefacility 140 may be located at the enterprise facility 102, where theenterprise facility 102 maintains a degree of control. In embodiments, ahosted service may be provided, where the appliance 140 may still be anon-site black box to the enterprise facility 102, physically placedthere because of infrastructure requirements, but managed by a thirdparty, vendor, or the like.

Simple server facility 142 appliances may also be utilized across theenterprise facility's 102 network infrastructure, such as switches,routers, wireless routers, hubs 148, gateways, print servers 142, netmodems, and the like. These simple server facility appliances may notrequire configuration by the enterprise facility 102, but may requireprotection from threats via an end-point computer security facility 152.These appliances may provide interconnection services within theenterprise facility 102 network, and therefore may advance the spread ofa threat if not properly protected.

One way for a client facility 144 to be protected from threats fromwithin the enterprise facility 102 network may be a personal firewall. Apersonal firewall may be an application that controls network traffic toand from a client, permitting or denying communications based on asecurity policy. Personal firewalls may be designed for use byend-users, which may result in protection for only the computer on whichit's installed. Personal firewalls may be able to control networktraffic by providing prompts each time a connection is attempted andadapting security policy accordingly. Personal firewalls may alsoprovide some level of intrusion detection, which may allow the softwareto terminate or block connectivity where it suspects an intrusion isbeing attempted. Other features that may be provided by a personalfirewall may include alerts about outgoing connection attempts, controlof program access to networks, hiding the client from port scans by notresponding to unsolicited network traffic, monitoring of applicationsthat may be listening for incoming connections, monitoring andregulation of incoming and outgoing network traffic, prevention ofunwanted network traffic from installed applications, reportingapplications that make connection attempts, reporting destinationservers with which applications may be attempting communications, andthe like. In embodiments, the personal firewall may be provided by thetreat management facility 100.

Another important component that may be protected by an end-pointcomputer security facility 152 is a network firewall facility 138, whichmay be a hardware or software device that may be configured to permit,deny, or proxy data through a computer network that has different levelsof trust in its source of data. For instance, an internal enterprisefacility 102 network may have a high level of trust, because the sourceof all data has been sourced from within the enterprise facility 102. Anexample of a low level of trust is the Internet 154, because the sourceof data may be unknown. A zone with an intermediate trust level,situated between the Internet 154 and a trusted internal network, may bereferred to as a “perimeter network”. Since firewall facilities 138represent boundaries between threat levels, the end-point computersecurity facility 152 associated with the firewall facility 138 mayprovide resources that may control the flow of threats at thisenterprise facility 102 network entry point. Firewall facilities 138,and associated end-point computer security facility 152, may also beassociated with a network node that may be equipped for interfacingbetween networks that use different protocols. In embodiments, theend-point computer security facility 152 may provide threat protectionin a plurality of network infrastructure locations, such as at theenterprise facility 102 network entry point, i.e. the firewall facility138 or gateway; at the server facility 142; at distribution pointswithin the network, i.e. the routers and hubs 148; at the desktop ofclient facility 144 computers; and the like. In embodiments, the mosteffective location for threat detection may be at the user's computerdesktop end-point computer security facility 152.

The interface between the threat management facility 100 and theenterprise facility 102, and through the appliance facility 140 toembedded end-point computer security facilities, may include a set oftools that may be the same for all enterprise implementations, but alloweach enterprise to implement different controls. In embodiments, thesecontrols may include both automatic actions and managed actions.Automatic actions may include downloads of the end-point computersecurity facility 152 to components of the enterprise facility 102,downloads of updates to existing end-point computer security facilitiesof the enterprise facility 102, uploaded network interaction requestsfrom enterprise facility 102 components to the threat managementfacility 100, and the like. In embodiments, automatic interactionsbetween the enterprise facility 102 and the threat management facility100 may be configured by the threat management facility 100 and anadministration facility 134 in the enterprise facility 102. Theadministration facility 134 may configure policy rules that determineinteractions, such as developing rules for accessing applications, as inwho is authorized and when applications may be used; establishing rulesfor ethical behavior and activities; rules governing the use ofentertainment software such as games, or personal use software such asIM 162 and VoIP 164; rules for determining access to enterprise facility102 computing resources, including authentication, levels of access,risk assessment, and usage history tracking; rules for when an action isnot allowed, such as whether an action is completely deigned or justmodified in its execution; and the like. The administration facility 134may also establish license management, which in turn may furtherdetermine interactions associated with a licensed application. Inembodiments, interactions between the threat management facility 100 andthe enterprise facility 102 may provide threat protection to theenterprise facility 102 by managing the flow of network data into andout of the enterprise facility 102 through automatic actions that may beconfigured by the threat management facility 100 or the administrationfacility 134.

Client facilities 144 within the enterprise facility 102 may beconnected to the enterprise facility 102 network by way of wired networkfacilities 148 or wireless network facilities 150. Client facilities 144connected to the enterprise facility 102 network via a wired facility148 or wireless facility 150 may receive similar protection, as bothconnection types are ultimately connected to the same enterprisefacility 102 network, with the same end-point computer security facility152, and the same threat protected enterprise facility 102 environment.Mobile wireless facility 150 clients 144, because of their ability toconnect to any wireless 150 network access point, may connect to theinternet 154 outside the enterprise facility 102, and therefore outsidethe threat-protected environment of the enterprise facility 102. In thisinstance the mobile client facility 144, if not for the presence of theend-point computer security facility 152 may experience a malware attackor perform actions counter to enterprise facility 102 establishedpolicies. In addition, there may be a plurality of ways for the threatmanagement facility 100 to protect the out-of-enterprise facility 102mobile client facility 144 that has an embedded end-point computersecurity facility 152, such as by providing URI filtering in personalrouters, using a web appliance as a DNS proxy, or the like. Mobileclient facilities 144 that are components of the enterprise facility 102but temporarily outside connectivity with the enterprise facility 102network, may be provided with the same threat protection and policycontrol as client facilities 144 inside the enterprise facility 102. Inaddition, mobile client facilities 144 may receive the same interactionsto and from the threat management facility 100 as client facilities 144inside the enterprise facility 102, where mobile client facilities 144may be considered a virtual extension of the enterprise facility 102,receiving all the same services via their embedded end-point computersecurity facility 152.

Interactions between the threat management facility 100 and thecomponents of the enterprise facility 102, including mobile clientfacility 144 extensions of the enterprise facility 102, may ultimatelybe connected through the internet 154. Threat management facility 100downloads and upgrades to the enterprise facility 102 may be passed fromthe firewalled networks of the threat management facility 100 through tothe end-point computer security facility 152 equipped components of theenterprise facility 102. In turn the end-point computer securityfacility 152 components of the enterprise facility 102 may upload policyand access requests back across the internet 154 and through to thethreat management facility 100. The Internet 154 however, is also thepath through which threats may be transmitted from their source. Thesenetwork threats may include threats from a plurality of sources,including websites 158, e-mail 160, IM 162, VoIP 164, applicationsoftware, and the like. These threats may attempt to attack a mobileenterprise facility 102 client facility 144 equipped with an end-pointcomputer security facility 152, but in embodiments, as long as themobile client facility 144 is embedded with an end-point computersecurity facility 152, as described above, threats may have no bettersuccess than if the mobile client facility 144 where inside theenterprise facility 102.

However, if the mobile client facility 144 were to attempt to connectinto an unprotected connection point, such as at a secondary location108 that is not a part of the enterprise facility 102, the mobile clientfacility 144 may be required to request network interactions through thethreat management facility 100, where contacting the threat managementfacility 100 may be performed prior to any other network action. Inembodiments, the client facility's 144 end-point computer securityfacility 152 may manage actions in unprotected network environments suchas when the client facility 144 is in a secondary location 108 orconnecting wirelessly 150 to a non-enterprise facility 102 wirelessinternet 154 connection, where the end-point computer security facility152 may dictate what actions are allowed, blocked, modified, or thelike. For instance, if the client facility's 144 end-point computersecurity facility 152 is unable to establish a secured connection to thethreat management facility 100, the end-point computer security facility152 may inform the user of such, and recommend that the connection notbe made. In the instance when the user chooses to connect despite therecommendation, the end-point computer security facility 152 may performspecific actions during or after the unprotected connection is made,including running scans during the connection period, running scansafter the connection is terminated, storing interactions for subsequentthreat and policy evaluation, contacting the threat management facility100 upon first instance of a secured connection for further actions andor scanning, restricting access to network and local resources, or thelike. In embodiments, the end-point computer security facility 152 mayperform specific actions to remediate possible threat incursions orpolicy violations during or after the unprotected connection.

The secondary location 108 may have no end-point computer securityfacilities 152 as a part of its computer components, such as itsfirewalls 138, servers 142, clients 144, hubs 148, wireless hubs 150,and the like. As a result, the computer components of the secondarylocation 108 may be open to threat attacks, and become potential sourcesof threats, as well as any mobile enterprise facility 102 clients 144that may be connected to the secondary location's 108 network. In thisinstance, these computer components may now unknowingly spread a threatto other components connected to the network.

Some threats may not come directly from the Internet 154, such as fromnon-enterprise facility 102 controlled mobile devices that arephysically brought into the enterprise facility 102 and connected to theenterprise facility 102 client facilities 144. The connection may bemade from direct connection with the enterprise facility's 102 clientfacility 144, such as through a USB port, or in physical proximity withthe enterprise facility's 102 client facility 144 such that a wirelessfacility 150 connection can be established, such as through a Bluetoothconnection. These physical proximity threats 110 may be another mobilecomputing device, a portable memory storage device, a mobilecommunications device, or the like, such as CDs and DVDs 170, memorystick 174, flash drive 174, external hard drive, cell phone 178, PDAs180, MP3 players, digital cameras, point-to-point devices, digitalpicture frames, digital pens, navigation devices, appliances, and thelike. A physical proximity threat 110 may have been previouslyinfiltrated by network threats while connected to an unprotected networkconnection outside the enterprise facility 102, and when connected tothe enterprise facility 102 client facility 144, pose a threat. Becauseof their mobile nature, physical proximity threats 110 may infiltratecomputing resources in any location, such as being physically broughtinto the enterprise facility 102 site, connected to an enterprisefacility 102 client facility 144 while that client facility 144 ismobile, plugged into an unprotected client facility 144 at a secondarylocation 108, and the like. A mobile device, once connected to anunprotected computer resource, may become a physical proximity threat110. In embodiments, the end-point computer security facility 152 mayprovide enterprise facility 102 computing resources with threatprotection against physical proximity threats 110, for instance, throughscanning the device prior to allowing data transfers, through securityvalidation certificates, through establishing a safe zone within theenterprise facility 102 computing resource to transfer data into forevaluation, and the like.

Now that the overall system has been described, we turn towards a set ofcontextual scanning embodiments. It should be understood that thefollowing embodiments may be managed through a threat managementfacility 100 along with other services, such as those described herein.

One aspect of secure computing is the scanning of data as it is receivedfrom a source for the purpose of blocking that data, such as for thescanning and identification of malware, confidential materials,restricted materials, inappropriate materials, and the like. One knownmethod for the blocking of received data employs blacklists for theblocking of known sources of data, where lists of URIs, users,locations, addresses, and the like, are accumulated as they are found tomatch the content that is to be blocked. However, individuals bent oncircumventing blacklists often obfuscate their source, such as bychanging their URIs. As such, blacklists may be ineffectual inidentifying these files for actions.

In embodiments, identifying content through a scanning facility may bedone for a number of reasons. One reason may be the potential forunintentionally receiving malware, and the need to block the malwareupon reception before the malware has the chance to do any damage.Traditionally, one way malware may be identified is with identity filesutilized by the scanning facility. However, the chances of identifyingthe malware may be greatly increased if the scanning facility is able toscan the received content in light of some information associated withthe file, the address, the URI, the source, the sender, and the like.Similarly, this technique may be used against file transfers that arepotentially less malicious, such unauthorized transfers, downloading oruploading confidential files from within or outside an enterprise, thedownloading or transfer of inappropriate content, and the like. Thepresent invention may allow for a technique, where the content beingretrieved, and information associated with the request or source of theinformation, may both be made available to the scanning facility toincrease the potential for targeted content to be identified.

In embodiments, the present invention may provide a way to examine thereceived data for contextual information that may indicate the source ofthe data being scanned for. This contextual information may take aplurality of forms, such as being a part of a changing address sequence,a pattern in the way a file is delivered, a pattern in the way a file issourced, the locale of the file, and the like. The information may beconsidered contextual in that it may be information that accompanies,proceeds, follows, is embedded, and the like, in the data that isreceived. The present invention may identify and store the contextualinformation for use in a scanning facility, where the scanning facilitymay utilize both the contextual information and the received data inidentifying target content. In embodiments, policy management 112 may beassociated with the process of the present invention, such as byproviding storage of contextual information, client requestrestrictions, locale restrictions, policy rules defining what content isto be scanned for, policy rules specifying actions to be taken, and thelike.

In embodiments, contextual information may be used in scanning inassociation with a client request, where the user request is examinedfor contextual information in conjunction with policy management 112 andused along with the retrieved content during scanning. Contextualinformation associated with the request by the client may containpatterns that may be utilized during scanning for the identification oftarget content to be blocked. This pattern may be a static pattern, achanging pattern, an unchanging pattern, a sequence that has beenpreviously stored as a part of policy management 112, a patternrecognized by an identity file that is part of the scanning facility,and the like. For example, the contextual information may be anunchanging portion of a received address or data, where the changingportion is the portion providing unique information to avoidblacklisting. Further, the pattern may be realized across a sequence ofaddresses, such as breaking the delivery of content into a series ofsub-deliverables, each with their own address. For instance, malware maybe configured for delivery to a client machine with a unique sequence ofaddresses, such as www.badaaa.com, www.badbbb.com, www.badccc.com, andthe like. These addresses may never have been used before, and thereforemay not be included on any blacklist. Upon reception of the firstaddress in the series, some characteristic may be recognized, such as anunusual embedded sequence, a recognized embedded sequence, and the like,and action may be taken upon scanning the retrieved content along withthis contextual information. On the other hand, the contextualinformation noted in the first address might not be enough evidence towarrant immediate action, but similar looking addresses may be watchedfor thereafter, and thus allow the scanning facility to be ready to helpidentify a subsequently received address. In this way, contextualinformation associated with a client request may be used in conjunctionwith the retrieved content to improve the chances for the scanningfacility to identify a targeted content.

In embodiments, contextual information may be used in scanning inassociation with a requested file and the locale of the machineproviding the file, where the locale information associated with thesource machine may be used along with the retrieved file in scanning thefile for target content to be blocked. For example, a first client mayrequest a file from a second client. The second client, representing thesource locale for the file, may provide contextual information in theform of locale information. Locale information may in turn be used inconjunction with policy management locale restrictions to improve theability for the scanning facility to identify and block targetedcontent. In embodiments, the blocking based on locale contextualinformation may be realized through policy management restrictions,policy management rules, identity files associated with the scanningfacility, and the like. In this way, contextual information associatedwith locale information may be used in conjunction with the retrievedcontent to improve the chances for the scanning facility to identify atargeted content.

FIG. 2 depicts a flow diagram for contextual scanning in associationwith a client request. To describe the flow diagram, reference will bemade to FIG. 1, although it is understood that the flow diagram may beimplemented in any other suitable environment or system. Further, theprocess flow embodiment is only an example and must not be taken inlimiting sense.

At step one 202 of the flow diagram, a client in the client facility 144may request access to a computing resource. Examples of the computingresource may be a computing application like a software file, a webpage, an instant messaging service, a peer-to-peer file-sharing service,a VOIP service, a VPN service and the like. Examples of the computingresource may also be a network resource like an externalnetwork/location or it may be an external computer device. Anotherexample of the computing resource requested by a client may be a requestfor a URI. A URI is a set of characters for identifying a resource in acomputing environment. In an example, a URI may be a Uniform ResourceLocator (URL). A URL is a URI that may identify a website address andmay also identify the protocol that can be used to access the address.For example, the URL http://www.abcd.com may identify the web address ofan organization “abed”. The URL also identifies the protocol foraccessing the website i.e. HTTP. In another example, a URI may be aUniform Resource Name (URN). A URN is a URI that identifies a resourcebut does not specify its location. An example of a URN may be anamespace rule for identification of MPEG metadata. In an embodiment,the client in the client facility 144 may request access to a URL, forexample, the website http://www.abcd.com. Note that the URIhttp://www.abcd.com is used herein as an example URI, and is notintended to be limiting in any way.

In embodiments, the client in the client facility 144 may request thenetwork server facility 142 for accessing the URI http://abcd.com. Thenetwork server facility 112 may include a web server that provides theclient with access to the requested URI. In an example, the networkserver facility 142 may include appliances like routers, gateways, hubs,and the like, which can be utilized by the web server to provide theclient with access to the requested URI. The network server facility 142may interact with the threat management facility 100 through theInternet 154 to provide the client facility 144 with access to therequested URI. In an embodiment, the policy management facility 112 inthe threat management facility 100 may be used to provide the client inthe client facility 144 with access to the requested URI. The policymanagement facility may control access of the client facility 144 to thenetwork resources of the enterprise facility 102. The policy managementfacility 112 may be a set of rules or policies that may indicate accesspermissions for the client facility 144, such as access permissionsassociated with the network, applications, external computer devices,and the like. In an embodiment, the policy management facility 112 mayinteract with the network access rules facility 124 for storing the setof rules or policies that may indicate access permissions for the clientfacility 144. The policy management facility may maintain restrictionsassociated with network requests. In an example, the networkrestrictions may include a list of URIs having known sources of malwareor known suspicious IP addresses or domains.

At step two of the flow diagram, in an embodiment, the restrictions inthe policy management facility 112 are reviewed in relation to theclient request. In an example, the restrictions in the policy managementfacility 112 may include a list of URIs. At step three 204, it isdecided whether the client request for access to a URI http://abcd.comshould be allowed or denied based on the restrictions in the policymanagement facility 112. In an embodiment, if the URI http://abcd.com isin the list of restricted URIs with respect to a client request, theclient request may be denied. In another embodiment, the network accessrules facility 124 may be used to provide the client in the clientfacility 144 with access to the requested URI. The network access rulesfacility 124 may have a generic set of rules that may be in support ofan enterprise facility's 102 network access policies, such as denyingaccess to certain types of URIs.

In embodiments, if the URI http://abcd.com is not in the list ofrestricted URIs with respect to a client request, the process flowproceeds to step four 208 and step five 210. At step four 208,contextual information related to the client request is stored. In anembodiment, the administration facility 134 may extract the contextualinformation and store it in the policy management facility 112. Thestored contextual information may be used in scanning for identificationof malware, confidential materials, restricted materials, inappropriatematerials, and the like. The contextual information may include datathat is used for indicating the source or origin of the requested URI.The contextual information may be a part of a changing address sequence,a pattern in the way the URI is delivered, a pattern in the way the URIis sourced, the locale of the URI, and the like. The information may beconsidered contextual in that it may be information that accompanies,proceeds, follows, is embedded, and the like, in the URI that isrequested.

At step five 210, the content in association with the client request isretrieved. In an example, the content associated with a client URIrequest may be the website content. In another example, if the URIrequested by the client is a file download (HTTP download) through aURI, the retrieved content associated with the client request is thedownloaded file. The content associated with the client request may beretrieved using a web server in the network server facility 142.

Thereafter, at step six 212, the scanning facility may utilize thestored contextual information to scan the retrieved content, to make aninformed decision about granting the client in the client facility 144access to the requested URI. In an embodiment, the scanning facility maybe an Anti-Virus (AV) Engine that is associated with the securitymanagement facility 122, the client, a network component, and the like.In embodiments, the scanning facility may provide for the scanning of aplurality of different types of content as discussed herein. Thescanning facility may scan the retrieved content for identifying contentthat needs to be blocked. In an example, the scanning facility may scanthe retrieved content associated with the URI requested by the client.Content that may need to be blocked as a result of scanning by thescanning facility may be malware, confidential materials, restrictedmaterials, inappropriate materials, and the like. In an embodiment, thescanning facility may access the policy management facility 112 toreview the restrictions associated with the client request. The scanningfacility may use the stored contextual information along with the clientrequest restrictions for scanning retrieved content. In an example, thestored contextual information may be a source of the requested URI likea particular country of origin. The scanning facility may block clientaccess to this URI if the client restrictions in the policy managementfacility 112 indicate blocking access to URIs originating from theparticular country of origin. In embodiments, virus identity files mayalso be used by the scanning facility for scanning the retrievedcontent. The virus identity files may include definitions andinformation for identifying malicious code. In an example, the virusidentity files may be part of the definitions facility 114.

FIG. 3 depicts a flow diagram embodiment for contextual scanning inassociation with the locale of a requested file. To describe the flowdiagram, reference will be made to FIG. 1, although it is understoodthat the flow diagram may be implemented in any other suitableenvironment or system. Further, the process flow embodiment is only anexample and must not be taken in limiting sense.

At step one 302 of the flow diagram, a client in the client facility 144may request access to a computing file. In an embodiment, a client inthe client facility 144 may request any other client for a file. Theclient having the requested file may be a machine or a computer system.For example, a client “A” may request a client “B” for the file, andboth the client “A” and client “B” may be a part of the enterprisefacility 102. In another example, client “A” may be a part of theenterprise facility 102 and the client “B” may be a part of an externalnetwork.

In embodiments, the request for the file may be routed through thenetwork server facility 142. The network server facility 142 may includeappliances like routers, gateways, hubs, and the like, which can beutilized to service the client request for the file.

At step two 304 of the flow diagram, the requested file is retrieved. Inan example a gateway may be used by the network server facility 142 toretrieve the requested file. Thereafter, at step three, the restrictionsin the policy management facility 112 are reviewed in relation to theclient request. In an example, the restrictions in the policy managementfacility 112 may include locale restrictions. The locale restrictionsmay specify restrictions with respect to the location of the machine orthe computer system having the requested file.

At step four 308 of the flow diagram, the locale information of thesource machine is identified. In an embodiment, locale information maybe part of contextual information associated with the requested file. Inan embodiment, the administration facility 134 may extract the localeinformation of the source machine having the requested file. The localeinformation may include an IP address of the machine having therequested file. In an example, the locale information may include anetwork address of the network having the machine storing the requestedfile. Thereafter, the identified locale information is fed to the policymanagement facility 112.

At step five 310, the requested file and the list of locale restrictionsfrom the policy management facility 112 are provided as input to ascanning facility. The scanning facility also has access to the localeinformation of the requested file that has been identified earlier. Inan embodiment, the scanning facility may be an Anti-Virus (AV) Engine.The scanning facility may utilize the locale restriction information andthe contextual information related to the locale of the source machineto decide whether to block access to the requested file.

FIG. 4 depicts a flow diagram embodiment for detecting restrictedcontent by analyzing contextual information and retrieved contentassociated with the requested content. To describe the flow diagram,reference will be made to FIG. 1, although it is understood that theflow diagram may be implemented in any other suitable environment orsystem. Further, the process flow embodiment is only an example and mustnot be taken in limiting sense.

At step 402, a client request for content is received. In embodiments,the client request for content is presented to the network serverfacility in the enterprise facility 102. The network server facility 142may include an application server facility, a web server facility, aservice provider's mail server facility and the like, for providing theclient with access to the requested content. In an example, the clientmay be a web browser client facility 144 connecting to the web serverfacility 142 for requesting access to a website. In another example, theclient may be an e-mail client facility 144 connecting to a serviceprovider's mail storage server facility 142 through the internet 154 torequest access to an email.

In embodiments, the requested content may be requested by a client inthe client facility 144. The requested content may include a computingresource. Examples of the computing resource may be a computingapplication like a software file, an instant messaging service, apeer-to-peer file-sharing service, a VOIP service, a VPN service and thelike. Examples of the computing resource may also be a network resourcelike an external network/location or it may be an external computerdevice. Another example of the computing resource requested by a clientmay be a request for a URI.

In embodiments, the content requested by the client may be associatedwith at least one of multiple IP addresses. For example, the client mayrequest for content from a machine in a network, where the networkincludes multiple machines and each machine is represented by an IPaddress.

In embodiments, the content requested by the client may be associatedwith at least one of multiple servers. In an example, the server may bean enterprise server. For example, the client request for content isprovided to at least one of an application server facility, a web serverfacility, a service provider's mail server facility and the like in thenetwork server facility 142. In another example, the enterprise servermay be under the control of an administrator. In yet another example,the server may be a root name server. The root name server may be a DNSserver that answers requests for a root domain and routes requests toother name servers.

In embodiments, the content requested by the client may be an address.Examples of the address may be a web address, an origin address, adestination address, an email address, a network address, an addressassociated with a device ID, an address associated with a digitalcertificate and the like. In an example, the address associated with adevice ID may be a Media Access Control (MAC) address or EthernetAddress for a network adapter in a computer network.

In embodiments, the content requested by the client may be a URI. Anexample of the URI may be a uniform resource identifier (URI). In anembodiment, the URI may include a domain name. A domain name is acomponent of a URI that identifies a computer on the Internet. Forexample, the domain name www.abcd.com in the URI http://www.abcd.comidentifies the web address of an organization “abed” on the internetthat can be accessed through the HTTP protocol. In embodiments, thedomain name may be a registered domain name, a top-level domain name andthe like. A registered domain name is a name that a domain nameregistrar provides to a customer. For example, in the URIhttp://www.abcd.com, the registered domain name abcd.com may be providedto an organization “abed”. A top-level domain name is the last part ofthe domain name i.e. the characters following the dot in any domainname. For example, in the URI http://www.abcd.com, the letters com isthe top-level domain name. In an example, the top-level domain name maybe associated with a country. For example, the domain namehttp://www.abcd.uk may be the web address of the organization “abed” inthe United Kingdom (UK). In other embodiments, the domain name may beassociated with a voice over Internet protocol (VoIP) service, domainkeys, an email and the like.

In embodiments, if the content requested by the client is a URI, the URImay include a sub-domain name. A sub-domain is a domain that is part ofthe domain name. For example, the sub-domain en.abcd.com may be asub-domain of the URI http://abcd.com that specifies the website of theorganization “abed” in English language. Similarly, the sub-domainfr.abcd.com may specify the French language website of the organization“abed”. In this embodiment, the sub-domain may be associated with aserver.

In other embodiments, the URI may be associated with multiple domainnames or with URI redirection. Multiple domain names may be used by anorganization for multiple identities. For example, an organization“abed” manufacturing electric motors may use two domain names“acmotors.abcd.com” and “dcmotors.abcd.com” both directing users to thecommon website http://abcd.com listing the products under the categories“motors”. URI redirection is used by organizations for registeringmultiple URIs for the same webpage in order to get unrestricted accessto users. For example, an organization “http://abcd.com” may alsoregister the URIs “http://abcdf.com” or http://abcds.com” so that animproperly typed URI name by a user may direct the user to theorganization's web page. In an embodiment, the URI may include a hostname.

In embodiments, the content requested by the client may be a location.In an example, a URI requested by a client may specify a location.Examples of the location may be a geographic location, a businesslocation, a residence location, a government location, a publiclocation, a private location, a network location, a server location, adistrict, a region, a vicinity and the like. For example the URIhttp://abcd.uk may specify the webpage of the organization in UnitedKingdom (UK).

At step 404, contextual information related to the client request issaved. Contextual information may be defined as data that indicatessource of the requested content. The data may be considered contextualin that it may be information that accompanies, proceeds, follows, isembedded, and the like, in the data that is requested. In an embodiment,the contextual information may be stored in the policy managementfacility 112. In an example, the administration facility 134 may extractthe contextual information from the requested content and store it inthe policy management facility 112. In embodiments, the contextualinformation may be used for scanning content requested by the client inorder to block or provide remedial action for restricted content.

In embodiments, contextual information associated with the contentrequested by the client may contain patterns that may be utilized duringscanning for the identification of target content to be blocked. Thepattern may be a static pattern, a changing pattern, an unchangingpattern, a sequence that has been previously stored as a part of policymanagement 112, a pattern recognized by an identity file that is part ofthe scanning facility, and the like. For example, the contextualinformation may be an unchanging portion of a received address or data,where the changing portion is the portion providing unique informationto avoid blacklisting. Further, the pattern may be realized across asequence of addresses, such as breaking the delivery of content into aseries of sub-deliverables, each with their own address. For instance,malware may be configured for delivery to a client machine with a uniquesequence of addresses, such as www.badaaa.com, www.badbbb.com,www.badccc.com, and the like. These addresses may never have been usedbefore, and therefore may not be included on any blacklist. Uponreception of the first address in the series, some characteristic may berecognized, such as an unusual embedded sequence, a recognized embeddedsequence, and the like.

In embodiments, the contextual information may be associated with acharacter string within the client request. Examples of the charactermay be an alphanumeric character, an alphanumeric code character, anascii character and the like. For example, for a URIhttp://en.abcd.comrequested by the client has the character string“en.abcd.com” in the URI address. This string “en.abcd.com” may beidentified as contextual information and may be used later in scanningfor malware.

In embodiments, the contextual information may be associated with aportion of a character string within a plurality of client requests. Inthis embodiment, the plurality of client requests may be in a sequence.In this embodiment, the portion of the character string is changing froma first client request to a second client request. The changing may be achanging numerical sequence, a changing of an alphanumeric sequence, achanging of an alphanumeric code sequence, a changing that increases thevalue of the portion of the character string, a changing that decreasesthe value of the portion of the character string, a changing that may beassociated with a pattern of changing. In an example, successive clientrequests for downloading a particular file through the Internet 154 mayinvolve access to the following URIs having a changing character stringsequence: http://aaacnt (dot) info, http://bbbcnt (dot) info,http://ccccnt (dot) info, http://dddcnt (dot) info, http://eeecnt (dot)info, http://fffcnt (dot) info, http://gggcnt (dot) info. In thisexample, “cnt(dot) info” may be the portion of the character string thatmay be considered as contextual information, since it remains the samefor all the client requests.

In embodiments, the contextual information may be associated with aportion of a character string within a plurality of client requests,where the portion of the character string is an unchanged portion from afirst client request to a second client request. In this embodiment, theunchanged portion may be associated with malware detection. For example,the content received from the URI “http://en.abcd.com” and the URIhttp://en.abcd.uk have the unchanged portion “en” that might beassociated with malware being downloaded from both the websites.

In embodiments, the contextual information may be associated with aportion of a character string within a plurality of client requests,where the portion of the character string is compared to a library ofpreviously stored portions. The previously stored portions may be anunchanging portion or a changing portion. In an example, the policymanagement facility 112 may store a list of portions identified as“malware carrying”. The portions of a character string identified ascontextual information may be compared with the list of portions formalware detection.

In embodiments, the contextual information may be associated with aportion of a character string within a plurality of client requests,where the portion of the character string is associated with the pathtaken by the client request. An example of a path may includesub-directories in a complete URI name. For example, in the URIhttp://universityname/department/electrical.edu, the portion“/department/electrical.edu” may signify the path to the website of theelectrical engineering department. The path may be a relative path, anabsolute path and the like. In an example a URI requested by the clientmay be http://<domain name>(dot)<whatever>/dl/nnn/win32.exe. In thisexample, nnn which may be a 1->3 digit number is the path that may bethe contextual information used for scanning for restricted content.

In embodiments, the contextual information may be associated with aportion of a character string within a plurality of client requests,where the portion of the character string is associated with the domainof the client request. In this embodiment, the portion of the characterstring may change while the domain name stays unchanged. In an example,the portion of the character string may be associated with the path.

In embodiments, the contextual information may be associated with adownload. For example, the client may request a file download from theURI http://abcd.com. The downloaded file may be identified as contextualinformation i.e. it may be used in scanning for malware. In anotherembodiment, the contextual information may be associated with a detectedpattern in a sequence of URI requests.

In embodiments, the contextual information may be associated with pathinformation of the client request. The path information may include atleast one of a plurality of sub-path portions from the origin of theclient request to the location of the retrieved content. In anotherembodiment, the contextual information may be associated with pathinformation of the retrieved content. The path information may includeat least one of a plurality of sub-path portions from the location ofthe retrieved content to the origin of the client request.

In embodiments, the contextual information may be associated withinformation received along with the retrieved content. The informationmay be header information, path information, location information,domain information, IP address information, network information and thelike. For example, when the URI “http://abcd.com” is accessed, theheader and network information related to the website content may beconsidered as contextual information. In another example, the IP addressof the computer hosting the URI is received along with the URI contentand may be identified as contextual information.

At step 408, retrieved content in response to the client request ispresented. In an example, the retrieved content is presented to thethreat management facility 100. In this example, the retrieved contentmay be provided to a scanning facility which may be part of the threatmanagement facility 100.

In embodiments, the retrieved content may be web content. For example,the retrieved content may be content requested by the client on theWorld Wide Web. The web content may be text content. In an embodiment,the text content may be a document, a data file and the like. Forexample, the text file may be a Microsoft Word file or a PowerPointfile. In embodiment, the web content may be visual content. The visualcontent may be an image, a video, an animation file and the like. Inother embodiments, the web content may be an aural content, anapplication, an e-service, a web page, a blog, a search result, adiscussion board, an e-commerce site, a social network site, a download,a game, an email, an appropriate website, an inappropriate website andthe like.

In embodiments, the retrieved content may be associated with malware.The retrieved content may include malware that may be associated withspam, a virus, a worm, a Trojan horse, spyware, adware and the like.

In embodiments, the retrieved content may be confidential content. In anexample, the confidential content may be confidential to a company. Forexample content retrieved from the website http://www.abcd.com mightcontain confidential information of the company “abed”. In anotherexample, the confidential content may be confidential to a government ofto a country.

In embodiments, the retrieved content may be offensive content. Inexamples, the offensive content may be personally offensive,professionally offensive, sexually offensive and the like.

In embodiments, a client request restriction in association with apolicy facility may be provided. In embodiments, the policy managementfacility 112 stores a list of client request restrictions. Therestrictions are used in identifying content that may be blocked by ascanning facility. The restrictions may be known as restricted content.

In embodiments, the client request restriction is associated with thecontextual information from the client request. In an embodiment, thecontextual information includes an alphanumeric pattern associated withmalware. In an example, the client request restriction may berestriction associated with accessing a URI having a string portion“en.abcd”. The string portion might be a virus associated with theparent domain “http//www.en.abcd.com”. In an embodiment, thealphanumeric pattern may be a known alphanumeric string within theclient request. In another example, the pattern may be a sequence ofalphanumeric strings in a series of client requests. For example,malware may be configured for delivery to a client machine with a uniquesequence of addresses, such as www.badaaa.com, www.badbbb.com,www.badccc.com, and the like. In another embodiment, the contextualinformation includes a domain name pattern associated with malware. Thedomain name pattern may be associated with a series of client requests.For example, domain names not ending in “.com” or “.co.uk” might be inthe list of client request restrictions. Examples of such domain namesmay be http://<domain_name>(dot) ru, http://<domain_name>(dot) cn,whatever>http://<domain_name>(dot) biz. These domain names may bedomains having a history of hosting malware.

In embodiments, the client request restriction may be associated with acharacteristic of the retrieved content. In an example, for a client URIrequest, the characteristic of the URI domain may be a client requestrestriction. Examples of the domain characteristics may be age of thedomain, familiarity of the domain to the client facility 144,registration of the domain in a specific country, registration byspecific registrants and the like. In an embodiment, the characteristicmay be associated with an email message characteristic. The emailmessage characteristic may be associated with an email header, a mailinglist and the like. For example, emails from the mailing list“groups.yahoo.listofcompanies.com” might be restricted. In anotherembodiment, the characteristic may be a language characteristic. Thelanguage characteristic may be associated with a phrase. In an example,the phrase may be a slang. In another embodiment, the languagecharacteristic may be associated with at least one of words and phrasesin proximity to one another.

In embodiments, the client request restriction is associated with a typeof retrieved content. In examples, the type may be a webpage, adocument, a multimedia file and the like. The multimedia file may be avideo file, an audio file, an animation file, an advertisement and thelike. In other examples, the type may be an attachment, a download, anemail and the like.

In embodiments, the client request restriction may be associated withthe source of the content. In examples, the source of the content may bethe source of the downloaded content. For example, the source of thecontent may be the “name of the author” of a downloaded file. In otherexamples, the source of the content may be a local machine. For example,the source of the content may be a computer having an IP address“abcd.gyth.dfsr.xxxx” from which the content is downloaded in thenetwork. In this example, the local machine may have created the contentor may have copied the content. In embodiments, the source of thecontent may from outside an enterprise, for example, from outside theenterprise 102. In this example, the source of the content may be arouter or a hub connected to the enterprise 102 through the Internet154. In other embodiments, the source of the content may from inside theenterprise 102.

At step 412, the contextual information and the retrieved content isprovided to a scanning facility. The scanning facility might be a partof the threat management facility 100. In an example, the scanningfacility may be an Anti-Virus (AV) engine. The scanning facilityutilizes the contextual information provided at step 404 and theretrieved content provided at step 408 to detect restricted content. Therestricted content may be the list of restrictions in the policymanagement facility. In an example, the scanning facility may use theclient request restrictions stored in the policy management facility 144to detect restricted content. In an example, to detect malwareassociated with a requested URI, the scanning facility may provide theURI to a Virtual Data Language (VDL) file. The VDL file may examine theretrieved content and provide results to the scanning facility. In anexample, malware running on a client is attempting to perform a HTTPdownload of a file from the URI http://www.abcd.com through a gateway inthe enterprise facility 102. The scanning engine uses the contextualinformation associated with this download to scan the download formalware. The contextual information may be the IP address of the machinehosting the file. In case, this IP address is listed as “restricted dueto presence of malware in the restrictions in the policy facility 112,the scanning facility is able to detect the presence of malware.

In embodiments, the contextual information may be extracted from a URIincluded in the client request, where the extracted information may be aplurality of characters from the URI, may exclude the domain name, mayinclude address information irrespective of the domain name, may be adata pattern determined based on a study of how a malicious attacker ischanging the URI, and the like. In embodiments, the contextualinformation may be derived from a URI included in the client request,where data pattern information may be extracted from the URI andcompared to data patterns of target content to derive the contextualinformation. In embodiments, the scanning facility may be a local to theclient, a server based scanning facility, and the like. A client requestrestriction process may be provided in association with a policyfacility such that certain client requests are automatically denied. Inaddition, a remedial action may be performed on the client in responseto the scanning facility blocking of restricted content, where theremedial action may be a scan of a local drive for malicious software.

In embodiments, the scanning facility may also suggest remedial actionto the client in the client facility 144 based on the detection ofrestricted content. The remedial action may be performed by the remedialaction facility 128 in the threat management facility 100. In anembodiment, the scanning facility may block the access of a restrictedURI to the client. For example, a gateway in the scanning facility mayblock access of the URI to the client. In another embodiment, thescanning facility may send a data file to the requesting client with anotification message. For example, a gateway in the scanning facilitymay send a data file to the requesting client with a notificationmessage. The notification message may include an action to be performedby the client. The notification message may direct the client to parsedata in the message and decide an appropriate action. In an embodiment,the data from the data file may be written to the client machine but thedata file may be non-executable, thus avoiding any undesirable effect onthe client machine. In another embodiment, an identity will be triggeredin the virus database. Depending on the notification message, the clientmay obey an action dictated in the notification message. For example,the notification message may direct the client to delete the receivedfile. In another example, the client may parse data in the notificationmessage and decide appropriate action on the data file. An example ofthe appropriate action may be doing a special scan on the received filebefore opening the file and removing adware in the file using software.Another example of the appropriate action taken by the client may betriggering a query process to determine the malicious processresponsible for sourcing the requested content. Following the queryprocess, the client may identify the malicious process, may contain theprocess by blocking the process. In an example, the process may beblocked at a gateway in the enterprise facility 102. In another example,the client may be isolated from the network which is the source of themalicious process. In yet another example, the client in the clientfacility 144 may scan the retrieved content by itself to check forstealthing files, processes, or Registry Keys.

FIG. 5 depicts a flow diagram embodiment 500 for detecting malware byanalyzing contextual information and retrieved content associated withthe requested content. In embodiments, a client request for content maybe received 502, where contextual information from the client requestmay be saved 504. In embodiments, when the content is retrieved 508, itmay be presented, along with the associated contextual information, to amalware detection facility 512. In embodiments, the malware detectionfacility may be associated with the threat management facility 100.

FIG. 6 depicts a flow diagram embodiment 600 for detecting restrictedcontent associated with an electronic file. To describe the flowdiagram, reference will be made to FIG. 1, although it is understoodthat the flow diagram may be implemented in any other suitableenvironment or system. Further, the process flow embodiment is only anexample and must not be taken in limiting sense.

At step 602 of the flow diagram, an electronic file is presented on acomputing facility. The electronic file may be presented to a clientbased on a client request for a file. In an embodiment, a client in theclient facility 144 may request any other client for a file. The clienthaving the requested file may be a machine or a computer system. Forexample, a client “A” may request a client “B” for the file, and boththe client “A” and client “B” may be a part of the enterprise facility102. In another example, client “A” may be a part of the enterprisefacility 102 and the client “B” may be a part of an external network.

In embodiments, the request for the file may be routed through thenetwork server facility 142. The network server facility 142 may includeappliances like routers, gateways, hubs that can be utilized to servicethe client request for the file. In an example a gateway may be used bythe network server facility 142 to retrieve the requested file. In anexample, the gateway may be part of the enterprise facility 102. Inanother example, the gateway may be external to the enterprise facility102.

In embodiments, the electronic file may be retrieved from a file system.In other embodiments, the electronic file may be retrieved from anetwork. In an example, the file may be downloaded from a network. Thenetwork may be part of the enterprise facility 102 or external to it.Examples of electronic file may be a word processing document, a spreadsheet document, an image file, an audio file, a music file, an email, anapplication file, an executable file, a web page, a web content page, adatabase file, a source code file, an operating system file and thelike.

At step 604 locale information associated with the file is extracted. Inan embodiment, locale information may be part of contextual informationassociated with the requested file. In an embodiment, the administrationfacility 134 may extract the locale information of the requested file.The locale information may include IP address of the machine having therequested file. In an example, the locale information may includenetwork address of the network having the machine storing the requestedfile. In an example, the identified locale information is fed to thepolicy management facility 112.

In embodiments, locale information may be associated with a location ofthe file. Examples of location may be a geographic location, a businesslocation, residence location, a government location, a public location,a private location, a network location, a server location, a district, aregion, a vicinity and the like.

In embodiments, the locale information is associated with a domain name,a path, a file name and the like. In other embodiments, the localeinformation may be associated with file header information, a currentlocation, a previous location, a user location and the like.

At step 608, locale restrictions associated with the policy managementfacility 112 are provided. The policy management facility 112 may have alist of locale restrictions that may be used by a scanning facility torestrict access to restricted content. The locale restrictions may beassociated with the location of the computing facility. In an example,the locale restrictions may be associated with the location of thegateway in the enterprise facility 102 through which the file request isrouted. In another example, the locale information may be associatedwith the location of the client in the client facility 144.

In embodiments, the list of restrictions may include restricted contentassociated with application classification. Examples of applicationclassification may be malware, work product, personal, unapproved,restricted, allowed and the like.

In embodiments, the restricted content may be confidential content. Forexample, the confidential content may be company confidential orgovernment confidential.

In embodiments, the restricted content may be offensive content.Examples of offensive content may include content that is personallyoffensive, professionally offensive, sexually offensive, and the like.

At step 610, the locale information and the electronic file is presentedto a scanning facility. The scanning facility may be a part of thethreat management facility 100. The scanning facility utilizes thelocale information and the locale restrictions in the policy managementfacility 112 to help in the detection of restricted content associatedwith the file.

In embodiments, the locale information is used by the scanning facilityto determine reputation of the content. In examples, reputation of thecontent may be associated with source of the content, author of thecontent and the like. In examples, the author of the content may beassociated with an enterprise, may be associated with the location andthe like.

In embodiments, reputation of the content may be associated with time.Association of the reputation of the content with time includes time thecontent is created, the time the content is downloaded, the time thecontent is copied, the time the content is requested and the like.

In embodiments, the scanning facility may block access to a fileoriginating from the URI “http//www.badlocation.org” if in the list oflocale restrictions the URI “http//www.badlocation.org” is listed ascontaining a Trojan horse.

In embodiments, the scanning facility may provide for remedial action tothe client in the client facility 144 based on the detection ofrestricted content. The remedial action may be triggered by the remedialaction facility 128 in the threat management facility 100. For example,a gateway in the scanning facility may send a data file to therequesting client with a notification message. The notification messagemay include an action to be performed by the client. The notificationmessage may direct the client to parse data in the message and decide anappropriate action. In an embodiment, the data from the data file may bewritten to the client machine but the datafile may be non-executable,thus avoiding any undesirable effect on the client machine. In anotherembodiment, an identity will be triggered in the virus database.Depending on the notification message, the client may obey an actiondictated in the notification message. For example, the notificationmessage may direct the client to delete the received file. In anotherexample, the client may parse data in the notification message anddecide appropriate action on the data file. An example of theappropriate may be doing a special scan on the received file beforeopening the file and removing adware in the file using software. Anexample of the appropriate action may be doing a special scan on thereceived file before opening the file and removing adware in the fileusing software. Another example of the appropriate action taken by theclient may be triggering a query process to determine the maliciousprocess responsible for sourcing the requested content. Following thequery process, the client may identify the malicious process, maycontain the process by blocking the process. In an example, the processmay be blocked at a gateway in the enterprise facility 102. In anotherexample, the client may be isolated from the network which is the sourceof the malicious process. In yet another example, the client in theclient facility 144 may scan the retrieved content by itself to checkfor stealthing files, processes, or Registry Keys.

FIG. 7 depicts a flow diagram embodiment 700 for detecting malwareassociated with an electronic file. In embodiments, an electronic filemay be presented on a computing facility 702, where locale informationmay be extracted from the electronic file 704. In addition, there may belocale restrictions provided in association with a policy facility 708.The locale information and the electronic file may then be presented toa malware detection facility 710. In embodiments, the policy facility112 and/or the malware detection facility may be associated with thethreat management facility 100.

Contextual information associated with a client request for content,locale information associated with the client request, localeinformation associated with the retrieved content, and the like, may bepresented to a scanning facility along with the content. In embodiments,the synergy associated the presentation of content along with thisinformation may provide a benefit in the scanning process that betterenables the scanning facility to detect target content. In embodiments,as a result, the target content may be blocked, such as in the case ofunwanted content, malicious content, illegal content, confidentialcontent, and the like.

The elements depicted in flow charts and block diagrams throughout thefigures imply logical boundaries between the elements. However,according to software or hardware engineering practices, the depictedelements and the functions thereof may be implemented as parts of amonolithic software structure, as standalone software modules, or asmodules that employ external routines, code, services, and so forth, orany combination of these, and all such implementations are within thescope of the present disclosure. Thus, while the foregoing drawings anddescription set forth functional aspects of the disclosed systems, noparticular arrangement of software for implementing these functionalaspects should be inferred from these descriptions unless explicitlystated or otherwise clear from the context.

Similarly, it will be appreciated that the various steps identified anddescribed above may be varied, and that the order of steps may beadapted to particular applications of the techniques disclosed herein.All such variations and modifications are intended to fall within thescope of this disclosure. As such, the depiction and/or description ofan order for various steps should not be understood to require aparticular order of execution for those steps, unless required by aparticular application, or explicitly stated or otherwise clear from thecontext.

The methods or processes described above, and steps thereof, may berealized in hardware, software, or any combination of these suitable fora particular application. The hardware may include a general-purposecomputer and/or dedicated computing device. The processes may berealized in one or more microprocessors, microcontrollers, embeddedmicrocontrollers, programmable digital signal processors or otherprogrammable device, along with internal and/or external memory. Theprocesses may also, or instead, be embodied in an application specificintegrated circuit, a programmable gate array, programmable array logic,or any other device or combination of devices that may be configured toprocess electronic signals. It will further be appreciated that one ormore of the processes may be realized as computer executable codecreated using a structured programming language such as C, an objectoriented programming language such as C++, or any other high-level orlow-level programming language (including assembly languages, hardwaredescription languages, and database programming languages andtechnologies) that may be stored, compiled or interpreted to run on oneof the above devices, as well as heterogeneous combinations ofprocessors, processor architectures, or combinations of differenthardware and software.

Thus, in one aspect, each method described above and combinationsthereof may be embodied in computer executable code that, when executingon one or more computing devices, performs the steps thereof. In anotheraspect, the methods may be embodied in systems that perform the stepsthereof, and may be distributed across devices in a number of ways, orall of the functionality may be integrated into a dedicated, standalonedevice or other hardware. In another aspect, means for performing thesteps associated with the processes described above may include any ofthe hardware and/or software described above. All such permutations andcombinations are intended to fall within the scope of the presentdisclosure.

While the invention has been disclosed in connection with the preferredembodiments shown and described in detail, various modifications andimprovements thereon will become readily apparent to those skilled inthe art. Accordingly, the spirit and scope of the present invention isnot to be limited by the foregoing examples, but is to be understood inthe broadest sense allowable by law.

All documents referenced herein are hereby incorporated by reference.

1-22. (canceled)
 23. A method for operating a scanning facilityexecuting on processing circuitry, the method comprising: receiving arequest for content from a client at the scanning facility, the requestincluding an outbound network request from the client with a UniformResource Identifier (URI) including a domain for the URI; savingcontextual information from the request at the scanning facility,wherein the contextual information includes whether the URI isassociated with URI redirection; examining the request for compliancewith a management policy at the scanning facility; retrieving a contentitem responsive to the request at the scanning facility; and analyzing,with the scanning facility, the contextual information from the requestand the content item responsive to the request to detect whether thecontent item includes restricted content based on the management policy.24. The method of claim 23 wherein the contextual information includes achanged portion of the request relative to other requests from theclient.
 25. The method of claim 24 wherein the contextual informationfurther includes a unique sequence of addresses in the other requestsfrom the client.
 26. The method of claim 23 wherein access to the URIdirects the user to another web page.
 27. The method of claim 23 whereinanalyzing includes analyzing header information for the content itemresponsive to the request to detect whether the content item includesrestricted content from a list of restrictions in the management policy.28. The method of claim 23 further comprising executing the scanningfacility on the client.
 29. The method of claim 23 further comprisingexecuting the scanning facility on a remote threat management facility.30. The method of claim 23 further comprising blocking the restrictedcontent from the client.
 31. The method of claim 23 further comprisingperforming a remedial action on the client in response to the restrictedcontent.
 32. The method of claim 23 wherein contextual informationincludes path information in the request.
 33. The method of claim 23wherein the contextual information includes a character string withinthe request.
 34. The method of claim 23 wherein the contextualinformation includes header information in the request.
 35. The methodof claim 23 wherein the contextual information includes data indicatinga source of the request.
 36. The method of claim 23 wherein thecontextual information includes header information for the content itemretrieved in response to the request.
 37. The method of claim 23 whereinthe contextual information includes a plurality of network addresses fora prior sequence of client requests.
 38. A computer program productcomprising computer executable code embodied in a non-transitorycomputer readable medium that, when executing on a scanning facility,performs the steps of: receiving a request for content from a client atthe scanning facility, the request including an outbound network requestfrom the client with a Uniform Resource Identifier (URI) including adomain in the URI; saving contextual information from the request at thescanning facility, wherein the contextual information includes whetherthe URI is associated with URI redirection; retrieving a content itemresponsive to the request at the scanning facility; and analyzing, withthe scanning facility, the contextual information from the request andthe content item responsive to the request to detect whether the contentitem includes restricted content based on whether the URI is associatedwith URI redirection.
 39. The computer program product of claim 38wherein the contextual information further includes a changed portion ofthe request relative to other requests.
 40. The computer program productof claim 39 wherein access to the URI directs the user to another webpage.
 41. The computer program product of claim 38 wherein analyzingincludes analyzing header information for the content item responsive tothe request to detect whether the content item includes restrictedcontent from a list of restrictions in a management policy.
 42. A systemcomprising: one or more hardware processors; a non-transitory computerreadable medium comprising instructions executable by the one or morehardware processors; and a scanning facility configured to receive arequest for content from a client, the request including an outboundnetwork request from the client with a Uniform Resource Identifier (URI)including a domain in the URI, wherein the scanning facility is furtherconfigured to save contextual information, including whether the URI isassociated with redirection, from the request at the scanning facility,analyze the request and the contextual information from the request,retrieve a content item responsive to the request, and block the contentitem from the client based on the analysis.